Winnti
Table of Contents
Overview
Backdoor:Win32/Winnti is the flagship modular cyber espionage platform and kernel rootkit family utilized by Chinese state-nexus threat group APT41 (also tracked as Winnti Group, Barium, Wicked Panda, and Double Dragon). Discovered in 2009 and continually modernized over more than a decade, Winnti specializes in software supply chain attacks, digital certificate theft, and intellectual property exfiltration against gaming, telecommunications, aerospace, and semiconductor corporations. Formally indicted by the US Department of Justice in September 2020, APT41 operators use Winnti to execute DLL side-loading via legitimate signed binaries, deploy malicious signed kernel-mode drivers to disable security defenses, and tunnel interactive command shells through custom encrypted protocols.
Known aliases
Threat reports may refer to this family under multiple names:
Threat Actor Attribution
Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.
- APT41 (Winnti Group / Barium / Wicked Panda) High confidence
Basis:
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Known Derivatives & Downstream Variants: Winnti V1 (2009 Gaming Build) · Winnti V2 64-Bit Rootkit · Winnti V3 Modular Platform · Winnti V4 Dll Side-Loader
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1195.002 | Compromise Software Supply Chain | initial-access | ATT&CK ↗ |
T1574.002 | DLL Side-Loading | defense-evasion | ATT&CK ↗ |
T1014 | Rootkit | defense-evasion | ATT&CK ↗ |
T1552.004 | Private Keys | credential-access | ATT&CK ↗ |
T1059.003 | Windows Command Shell | execution | ATT&CK ↗ |
T1071.001 | Web Protocols | command-and-control | ATT&CK ↗ |
T1547.001 | Registry Run Keys / Startup Folder | persistence | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
- T1071.001: Implement web filtering and SSL/TLS inspection to detect malicious command and control (C2) traffic hiding in HTTP/HTTPS.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-KMC | Kernel Memory Integrity Checking | Harden | T1014 | Enable Hypervisor-Protected Code Integrity (HVCI) and UEFI Secure Boot to prevent unsigned kernel driver execution. |
D3-PBA | Process Spawn Analysis | Detect | T1059.003 | Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe. |
D3-WAF | Web Content Filtering & Inspection | Filter | T1071.001 | Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
Exploited Vulnerabilities (CVEs)
This malware family is documented weaponizing the following common vulnerabilities and exposures:
- CVE-2019-19781 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
- CVE-2020-10189 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
Command & Control (C2) and Network Profile
How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.
| Protocols | TCP, UDP, HTTPS, DNS |
|---|---|
| Observed ports | 443, 53, 8080 |
| Identifiable from traffic alone | High |
Indicators of Compromise
Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.
File hashes (SHA-256, sample)
Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.
4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e
Delivery vectors
supply_chain_compromisespearphishing_attachmentscitrix_vpn_exploitation
Persistence mechanisms
Windows Service InstallationDLL Side-Loading Registry Keys
Tiered Detection Rules (Cisco CAIRN Model)
Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_WINNTI_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Winnti"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "winnti" ascii wide nocase
$s2 = "winnti" ascii wide nocase
$s3 = "winnti backdoor" ascii wide nocase
$s4 = "backdoor.winnti" ascii wide nocase
$s5 = "trojan:win32/winnti" ascii wide nocase
$s6 = "winnti trojan" ascii wide nocase
$s7 = "apt41 core backdoor" ascii wide nocase
$s8 = "winnti group malware" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Winnti (Backdoor) Execution & Triage
id: f20530c9-858c-5c90-9f71-4f8ea015567f
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Winnti malware family. Detects proxy execution, reflective DLL loading,
and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/winnti
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.backdoor
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1195_002
- attack.t1574_002
- attack.t1014
- attack.t1552_004
- attack.t1059_003
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \powershell.exe
- \cmd.exe
- \rundll32.exe
- \regsvr32.exe
CommandLine|contains:
- DownloadString
- IEX(
- '/s /n /u /i:'
- sc create
- start-process
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_WINNTI_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Winnti tradecraft"
tier = "T3 - Attribution Fingerprint"
confidence = "High (Confirmed Family Signature)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
// Core family identifier & heuristic payload signatures
$attrib_str = "winnti" ascii wide nocase
$pe_magic = "MZ" ascii
$net_marker = "http" ascii nocase
condition:
uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Engage a specialized Incident Response (IR) firm with APT threat actor experience immediately.
- Audit all corporate code-signing certificates and assume compromised digital keys must be revoked.
- Search enterprise environments for DLL side-loading behaviors and unbacked kernel driver registrations.
- Isolate compromised servers and conduct thorough forensic disk and memory imaging.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not treat Winnti as standard commodity malware; partial removal will cause the APT to activate backup implants.
- Avoid discussing incident response plans over compromised corporate email or unencrypted networks.
- Never allow untrusted signed kernel-mode drivers to load without strict driver signature enforcement (WHQL).
References & External Analysis
- US Department of Justice: Seven International Cyber Defendants, Including Five Chinese Hackers (APT41), Charged
- CISA Alert AA20-258A: Chinese Ministry of State Security-Affiliated Cyber Actors
- Novetta / Kaspersky: Operation Winnti Whitepaper and Research Analysis
- CISA Advisory: AA20-258A
- Search "winnti" on VirusTotal (External Analysis)
- Search "winnti" on Any.Run (Sandbox Sandbox)
- Search "winnti" on MalwareBazaar (Malware Samples)
North American Authority Advisory (CISA / NIST)
The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: AA20-258A ↗
Frequently Asked Questions
What is Winnti malware?
Winnti is an advanced modular cyber espionage backdoor and rootkit platform developed by Chinese state-sponsored threat group APT41.
Which threat actor operates Winnti?
Winnti is operated by APT41 (Winnti Group), whose members were formally indicted by the US Department of Justice in September 2020.
What is Winnti's signature execution method?
Winnti relies heavily on DLL side-loading, using legitimate, digitally signed executables to load malicious DLL payloads into memory.
How does Winnti evade endpoint detection systems?
Winnti deploys signed kernel-mode drivers to hide processes and hooks Windows network APIs to conceal unauthorized C2 communications.
What industries were targeted by Winnti campaigns?
Winnti campaigns targeted video game studios, telecommunications operators, pharmaceutical companies, and semiconductor manufacturers.
How do I remove the Winnti Backdoor from Windows?
Manual removal of Winnti is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
Is Winnti a virus or a Backdoor?
Winnti is classified as a Backdoor. Unlike traditional viruses that infect files, modern malware like Winnti typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Winnti infection?
Symptoms of Winnti can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Backdoors
Want to prevent Winnti and similar threats from compromising your organization? Read our comprehensive defensive guide: Backdoor & RAT Protection for Businesses.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/winnti.json
Ecosystem & Interactive Environments
This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.